To interact intensively with WebInput.NET process at runtime, there is an object oriented client side class library of WebInput.NET that can be modified via script and persisted to server side when post back. The client side object is actually a mini version of server side object with some extra client side features. Therefore, client side object has consistent object model reflected to server side object model.

WebInput.NET client side object model uses new class-engine model instead of function-based model for better performance and reduces memory usage. The class is holding information of an object while process and mechanism are handled by the engine. With this class-engine model, client side objects are running faster, more reliable and easy to use. The classes are visible but the engines are private and obfuscated so it is not intended to be used by end developers.

There are also several client side event handlers that can be attached. Every event handler provides minimum a controlId parameter as standard.

For details about WebInput.NET client side object model, please refer to the client side object model documentation section.

The client side object is actually a mini version of server side object with some extra client side features.

In the previous versions of Intersoft's components (as well as other vendor's components in the market), developers are forced to remember each function used to get the object for each product. For example,

For WebGrid.NET, developers should use wgGetGridById(id);

For WebCombo.NET, developers should use wcGetComboById(id);

Now with the new framework-based client object model, you no longer has to remember these functions. You can simply call one function to get any object that is a member of WebUI.NET Framework, for example:

var input1 = ISGetObject("WebInput1");

You can also use the same function to get the menu object, such as:

var menu1 = ISGetObject("WebMenu1");

With the new framework-based client object model, Intersoft redefines a new productivity level for developers while developing with Intersoft components which expose same familiarity and concept.

Previous version of Intersoft's components such as WebGrid.NET Professional V3.0, WebGrid.NET Enterprise V3.5 and WebCombo.NET V2.0 do not support the new framework-based client object model. It will be implemented in the next major version of the components.

Intersoft WebInput Documentation
Client Side Object Model
See Also Send Feedback

See Also